This a trade-off; Previously, we closed all connections when the active environment changed to avoid users not knowing which URL is currently used to connect if included some env.
Now, based on multiple tabs, we may have multiple WebSocket or grpc tabs from different workspaces, and we want to keep all the connections when the corresponding tab exists. When a workspace's active environment changes, finding which requests are affected and closing them will introduce more complexity.
So I just delete it and only close connection when tab close.

discuss with @ihexxa. I will try to emit an event through the event bus when modifying the active environment. So that we could get the workspaceId and filter the connections under the workspace then close them.

updated in this commit: f367b65

If user just closse all tabs in one org, will this also close connections from other organizations?

nit: it would be great if we can add short description for new hooks' usages and goal.

This should all ideally be modelled in the main context for consistency of implementation and in order to minimize bugs and surprises due to the deviation in implementation.

These logics will only run in the renderer process, so I think it is unnecessary to pass the event to the main process, to avoid the communication and IPC function code.
In my opinion, we could clarify the scope of the code according to the scenario. When the code is only effective in the rendering process, we need to try to avoid introducing it into the main process.
This eventbus class can be a common approach when we want to communicate between different components and not need the main process.

a react hook is a mechanism to wrap react features into a observable function for reuse.

close all connections appears to be a fire and forget behavior.

why introduce all this complexity?

This scenario is indeed a bit complicated, we can't simply know when to close a connection, such as clicking a button and then closing the connection in the callback.
The connection may be closed because the user closed the tab manually or the user deleted the request or workspace. Using eventbus can decouple the connection control logic from the tab. Also I think abstract these logic into this custom hook could make the debug.tsx component simpler to read, and put the connection control logic together for easy maintenance.

this use effect was clear about what happened and why, we close all connections when active env changes, the new hook is unclear about both of these questions.

Under the multiple-tabs scenario, when we switch to another tab that belongs to another workspace, activeEnvironment also changes and runs the logic in this useEffect. This is not as expected, we want to keep the connection when the tab exists, so we have to use another approach to implement it.